Knowledge flush — 12 insight(s) claimed: 8 ingested on this branch, 3 folded onto open PRs, 1 dropped as already merged

Run id 20260906-003715-45485 (headless auto-flush), branch knowledge/choiyounggi-20260906-003745, base origin/main at 6dcda6f (1.21.0). Claimed with queue-claim.js claim --max 12; 40 rows remain pending for later flushes.

Verified best-practice

Nothing was upgraded to verified without a cited document or a reproduction I ran; #8 and #11 are labelled field-tested in the pages.

Existing-layer check

Pages read: infrastructure-agent-orchestration-code-graph-as-orientation-layer, infrastructure-agent-orchestration-worktree-isolated-workers, infrastructure-agent-orchestration-session-context-token-budget, infrastructure-observability-alerting, testing-quality-tests-that-cannot-fail, testing-quality-injected-clock-duration-assertions, testing-async-async-testing, frontend-design-anti-slop-visual-design, databases-schema-design-online-schema-changes, databases-transactions-optimistic-vs-pessimistic-locking, databases-transactions-isolation-level-selection, backend-common-integrations-estimate-derived-thresholds

Also read INDEX.md, the domain indexes for infrastructure, testing, frontend, databases, backend, qa and debugging, AGENTS.md, templates/page.md, and, on the open PR branches only (not on this checkout), semantic-conflicts-after-parallel-merge (#179) and checkable-claims-in-an-adopted-plan (#181).

Overlaps and outcomes:

• knowledge: streaming large result sets (server-side cursor blocked → fetchmany + write-only) #1 OKLCH — anti-slop-visual-design has the "+3% lightness per elevation level" rule; not a conflict (elevation is decorative), but a reader could over-apply it to state cues. Created a new page and appended a pointer to that row plus a related: link both ways.
• knowledge: kubelet resource metrics on embedded k8s; host-to-pod memory limit sizing #2 benchmark-relative — no existing page; estimate-derived-thresholds (same bot, integrations) and mape-aligned-point-prediction (ml) are the neighbours. New page; back-link added on estimate-derived-thresholds.
• knowledge: PID-1 tee log capture pattern, BSD/GNU date %3N feature detection #3 multi-row reorder — isolation-level-selection has the multi-row-invariant row (SERIALIZABLE or parent lock) and optimistic-vs-pessimistic-locking the version-column path, but neither covers the unique-position constraint or the final-state rule. New page; both existing pages gained a related: back-link.
• knowledge: kubelet resource-metrics, PID1 log flush, date %3N detection #4 Prisma CONCURRENTLY — online-schema-changes already says "Never inside a transaction block" for CONCURRENTLY; merged two edge rows (implicit runner transaction; premise absent on an empty table), five sources, applies_to widened to prisma.
• ingest(databases): online schema changes + autovacuum/wraparound #5 graphify viz failure — merged as one edge row into code-graph-as-orientation-layer next to the exit-0 row it extends.
• knowledge: kubelet resource metrics, cgroupns visibility, LLM completion validation, gateway alias defaults (4 insights) #6 newest transcript — merged as one edge row into session-context-token-budget. Body-only edit: PR knowledge: 9 insights — fresh-context review, gate parser/executor split, coordinator under tmux, sun_path limit, REPL sentinel await, allowlist bypass reproduction, version-drift gate, mock ts at emit (+3 folds onto #180/#181, 1 stale drop) #183 rewrites that page's related: line, so the frontmatter was left untouched to avoid a conflict; the source is recorded in the body's Sources list.
• knowledge: validating a check whose target does not exist yet (1 insight) #7 fake-timer TTL — injected-clock-duration-assertions is about float tolerance, not this; tests-that-cannot-fail is at 114 body lines and its related: line is rewritten by knowledge: 12 insights — deny rules under bypass, merged-tree gate, worker verify command, Kotlin daemon heap, extracted-method this (+7 merges) #179 and knowledge: 9 insights — fresh-context review, gate parser/executor split, coordinator under tmux, sun_path limit, REPL sentinel await, allowlist bypass reproduction, version-drift gate, mock ts at emit (+3 folds onto #180/#181, 1 stale drop) #183. Merged into async-testing (fake-timer mechanics page) as one edge row, body-only for the same reason (knowledge: 9 insights — fresh-context review, gate parser/executor split, coordinator under tmux, sun_path limit, REPL sentinel await, allowlist bypass reproduction, version-drift gate, mock ts at emit (+3 folds onto #180/#181, 1 stale drop) #183 rewrites its related:), with an inline link to tests-that-cannot-fail for the mutation proof.
• knowledge: spec/mapping artifact checks — coverage vs value validity, per-check negative controls, GFM pipe parsing (2 insights) #8 fallback alert — merged into alerting as one edge row + one Instead-of row, body-only (knowledge: 12 insights — dropzone copy vs drop handlers, destination-in mask chaining, media-query inset reset, spatial clamp, env restore vs pop, synthetic-corpus floor, plan-claim recompute, multi-name command -v, alert suppression key, sibling validators (+2 folds) #181 rewrites its related: line).
• knowledge: doc-conformance check controls + object-storage key persistence (5 insights to 2 pages) #9, knowledge: spec-document gates (4 axes + controls) and non-ASCII grep matching #10, knowledge: non-interactive CLI hangs, gates that read command text, editing a gated document (4 insights → 3 pages) #11 — folded onto open PRs (next section), no main-branch page touched.
• knowledge: non-interactive CLI stdin, LLM response completeness, externally-owned defaults #12 — duplicate of a merged row; nothing written.

No contradictions found. Lint: wiki-structure-checks.js wiki → 0 findings (281 pages); wiki-lint-prohibitions.js wiki → 0 violations; new pages 83/78/88 total lines (all bodies ≤ 120).

Open-PR check

Open knowledge/* heads listed with gh pr list --search "head:knowledge/": #183 (knowledge/choiyounggi-20260904-133717), #182 (…-20260903-214027), #181 (…-20260903-203836), #180 (…-20260903-184706), #179 (…-20260903-172728). Each was fetched and diffed against origin/main -- wiki/.

Expected merge friction: every open head appends to log.md, and #179/#180 touch INDEX.md (2 lines each); this branch appends nine log.md lines and edits the databases and backend rows of INDEX.md. frontend/index.md and infrastructure/index.md are touched by #181/#179/#183 in other rows. These are line-adjacent, not semantic, conflicts.

Routing decision

No new category was created. Indexes updated: frontend/index.md, backend/index.md, databases/index.md, INDEX.md (databases and backend route lines); log.md gained nine entries.